Long term updates #46
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Ruby 2.3.3 is not the latest version in 2.3 series. Test that the project works in Ruby 2.3.4 and patch bugs if it doesn't. Plus, start testing compatibility with Ruby 2.4 series.
No bugs so far.
The file new_framework_defaults is dropped now since all the defaults have been merged and unit tests still validate.
Isn't it always a joy running app:update and letting Rails ask you if you want to remove all your configuration? I have learnt now that the best way for dealing with this is to just replace every file when app:update asks so, but then spend time using git add -p.
This seems to be something new on Rails 5.1.
App is fully ported to 5.1.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A few updates more complex than running gem update.
Update Ruby versions
Should keep the Ruby version running in the server up to date in order to be protected against possible threats. Ruby 2.3.3 is not the latest version. Test compatibility with Ruby 2.3.4 and patch properly if it fails. Start testing for Ruby 2.4.0. I tried this in the past and it fails with Ruby 5.0. Let's hope for a fix as well.
Update to Rails 5.1
5.0 will continue receiving security updates, but updating to Ruby 5.1 soon is a better idea.